WallControl 10 Errata
Video sources can potentially cause memory leaks in carousel.
Under current and previous driver versions placing two or more video sources consecutively in a carousel will cause a memory leak. This is true as of driver version 4.8.1.
Windows 10 Desktop scaling can cause window offset issues.
WallControl 10 requires desktop scaling be set to 100%. Any other scaling factor will cause window offset and size issues.
Before installing WallControl 10 on a Windows 10 machine the Windows feature set for .NET Framework 3.5 must be enabled.
You will need to manually add support for .NET Framework 3.5 using the Windows 10 Program and Features option dialog.
Server auto-discovery may not operate as expected.
Auto-discovery utilises UDP - due to the nature of UDP this may not function correctly on certain network configurations, depending on network topology. Contact your network administrator for advice concerning this. It should still be possible to manually add a server using the WallControl 10 client.
Possible issue using PuTTY in Active mode when connecting to WallControl 10 telnet server.
It is possible that the first two characters may be missing when performing an initial request using PuTTY set in Active mode. The problem is not observed when it is being used in Passive mode.
Vision sources should not be used with a non-zero buffer duration when in a carousel.
When adding a buffer duration to an Vision source within a carousel, starting and stopping the carousel will erroneously cause a permanent reduction in the maximum number of simultaneous captures available for that input until the WallControl 10 Server is restarted. As Vision sources do not benefit from having a buffer duration greater than 0 it is advised that the default buffer duration of 0 for Vision sources is not changed.
Z-Order for windows containing Quant sources maybe incorrect when opening layout files.
When layout files containing Quant sources are opened, the window z-order maybe different from when the layout was originally saved.
Rogue Quant processes may stop Quant to WallControl 10 Server communication.
Quant restarts itself after the server is closed. This stops the subsequent server processes communicating with Quant and may adversely affect how the server shuts down.
Possible issue when unsupported port is used for wall server.
When a wall port number is in the ephemeral port range (49152 to 65535), the wall may not start due to the port clashing with another application.
Known issue when retrieving a snapshot image of an SQX source for cropping
A valid snapshot must be returned within 30 seconds before the cropping interface times out gracefully.
Known issue when attempting to crop a Vision HDCP source
It is possible that the image snapshot returned for the HDCP source will look blurred and of low quality, this is due to the algorithm that is used to degrade the snapshot it will not affect the actual source when displayed.
Web sources zoom level behaviour.
The standard behaviour of Chrome when changing the zoom level on a web pages is to apply the same zoom level to all pages that use the same sub domain. This means that web sources that share a similar URL, will all zoom together when the setting is applied.
Web sources vertical scroll behaviour.
When setting a vertical scroll preset property to a web source that contains continuous scrolling content, such as Twitter or Instagram, the value may not be applied correctly on page load or refresh.
Issues with invalid Datapath Agent coordinates.
Creating a new port with invalid desktop coordinates in Datapath Agent will cause the wall to crash when attempting to open the connection as a source.
CLI Performance Issues.
As of 1.9.0 there is a potential decrease in the performance of some commands with regard to completion speed. However, in most cases this should not be discernible from previous versions.
SoftSQX sources may cause client disconnections.
In rare cases opening SoftSQX sources may cause the client to pause or disconnect.
Legacy Web Browser issue.
The Legacy Web Browser is slow to open and close. This may lead to client time out disconnections when editing or opening a layout containing multiple instances of the Web Browser.
OSD flickering in multiple windows.
OSD may flicker when added to a large number of windows.
OSD flickering with large fonts.
OSD may flicker when used in conjunction with large font sizes.
WallControl 10 installation issue (HASP).
When installing WallControl 10 on a clean system the HASP sentinel driver install may show a warning message. This manifests itself as the WallControl 10 install freezing mid installation. The message box is hidden behind the installation window, finding this and clicking OK will continue the installation.
WallControl 10 Client window move whilst frame applied.
Whilst Wall Frames are enabled, the frame area of a window representation in the client does not enable the move action. To move a window select the inner content (inside the thick red area) and drag.
Upgrade issue for the Wall Management 'Startup Layout' setting.
The Wall Management 'Startup Layout' setting may need to be re-applied after upgrading from versions before 1.12.0.
Word documents containing images may cause a memory leak.
Word documents containing embedded images may cause a memory leak in the long term if opened and closed very frequently.
Vision Streaming from VisionSC-UHD2 may result in downscaling.
Vision Streaming of sources from VisionSC-UHD2 cards will result in the stream being downscaled (by aspect ratio) to less than or equal to 4096x4096 if the original Vision source is larger than 4096x4096.
Ganged or VisionSC-DP2 Vision sources may be not streamed.
Ganged or VisionSC-DP2 Vision sources may not be streamed if the original Vision source is larger than 4096x4096 as these Vision captures cannot be downscaled.
Connection to Blueprint can fail if the machine name is changed
Changing the machine name of a wall controller can stop connections from remote clients. Please do not change the name of the wallcontroller machine.
Vision Streaming is not available on some systems
The Vision Streaming feature is not available on certain systems due to hardware constraints. Systems include:
WallControl 10 User Rights Management Errata
WallControl 10 User Rights Management does not register new source or layouts without a wall restart.
Any sources or layouts added after the wall is started will not be registered with URM without a wall restart.
WallControl 10 User Rights Management requires Active Directory.
WallControl 10 User Rights Management integrates only with Microsoft Active Directory; other providers will be added at a later date.
WallControl 10 User Rights Management must be manually enabled by the server.
In order for User Rights Management (URM) to be activated, the server must have a Pro license dongle installed in the server machine and the user must run the enable/disable (SecurityOnOff) program directly on the WallControl 10 server, this program must be run as an Administrator. If a pro dongle is not detected, security will not be accessible. If security is not explicitly enabled, security restrictions will not be applied. Please read the URM documentation regarding the setup and use of User Rights prior to activating.
User Rights Management source authorisation issue in WallControl 10 Client.
When certain types of sources are added using the WallControl 10 Client and default permissions have not been granted for the user's role, the source will still appear in the sources list for the client performing the operation. This behavior is specific to the client that adds the source. The source will not be visible for any other client that is connected, unless appropriate permissions have been granted.
User Rights Management default source refresh issue in Security Administration Client.
When media sources are added to any of the WallControl 10 Server media directories, the associated source entry may not be listed in the Security Administration Client until the WallControl 10 Server is re-started. This issue does not affect the default security permissions for the media source, which will be applied as per the documentation.
Renaming Blueprint wall whilst User Rights Management is enabled.
After renaming Blueprint wall with User Rights Management enabled, the “Wall” group permissions will require updating under the new wall name. If not updated, the walls on the server may not start or function correctly.